Offline Controller

Details

Storage Subsystem: Unnamed
Controller in slot B
Service action (removal) allowed: Yes
Service action LED on component: Yes
Enclosure: Controller/Drive enclosure
Replacement part number: 39R6502
Board ID: 1932
Submodel ID: 40
Serial number: SX80202969

What Caused the Problem?

The controller was placed Offline. This could be caused by the following:

The controller failed a diagnostic test and was automatically placed Offline. The diagnostics are initiated internally by the controller.
The controller was manually placed Offline.

The Recovery Guru Details area provides specific information you will need as you follow the recovery steps.

Caution: Possible loss of data accessibility. Do not remove a component when either (1) the Service action (removal) allowed (SAA) field in the Details area of this recovery procedure is NO, or (2) the SAA LED on the affected component is OFF (note that some products do not have SAA LEDs). Removing a component while its SAA LED is OFF may result in temporary loss of access to your data. Refer to the following Important Notes and the Recovery Steps for more detail.

Caution: Electrostatic discharge can damage sensitive components. Always use proper antistatic protection when handling components. Touching components without using a proper ground may damage the equipment.

Important Notes

If the new controller canister does NOT contain a battery, you will have to insert the battery from the old controller canister into the new replacement controller canister. Consult your hardware documentation for details.
Logical Drives assigned to the Offline controller have been moved to the storage subsystem's Online controller.
Service Action Allowed Important Information:
- The Service action (removal) allowed field in the Details area indicates whether or not you can safely remove the component. If the SAA field is NO, then the affected component must remain in place until you service another component first.
- The Service action LED on component field in the Details area indicates whether or not a physical SAA LED is present on the hardware component. This field does NOT indicate whether the LED is ON or OFF (that indication is provided by the Service action (removal) allowed field).
- If a component does not have an SAA LED, then it is OK to remove the component when its fault LED is lit and the Service action (removal) allowed field = YES in the Details area.
- The Service action (removal) allowed field shown in the Details area and the physical SAA LED on the hardware component (if supported) MUST match before you remove the affected component. In rare cases (such as multiple problems), the status of the LED and the SAA field may not match. If there is a mismatch, then you should NOT remove the component until these indications match. The Recovery Steps will help you to make this determination.

Recovery Steps

If...

Then...

You were instructed to manually place the controller Offline in another procedure

Go to step 2.

The controller was automatically placed Offline

Go to step 2.

You know the controller was manually placed Offline but there is nothing wrong with the controller

a	From the Support tab, click the Manage Controllers link.
b	Click the Place Controller Online or Offline link.
c	Place the controller listed in the Details area Online.
d	Go to step 8.

Check the Service Action Allowed status in the Details area for the offline controller.

If...

Then...

Service action (removal) allowed = YES

Check the Service action LED on component field in the Details area and then answer the following question:

Does the field indicate that this component has a physical SAA LED?

Yes - Check the physical component to ensure the LED is ON.
- If the LED is ON, then go to step 3.
- If the LED is OFF, then click the Recheck button to see if another problem appears in the Summary area.
  - If there is another problem, fix it first and then return to this procedure.
  - If there is no other problem, then stop this procedure and contact your technical support representative.
No - Go to step 3.

Service action (removal) allowed = NO

Answer the following question:

Are there other problems being reported in the Summary area?

Yes - Fix these problems first and then return to this procedure after clicking the Recheck button.
No - Stop this procedure and contact your technical support representative.

Remove the affected controller.

Refer to the Summary tab to view which management method you are using to manage this storage subsystem.

If...

Then...

You are using In-Band management for ALL hosts attached to this storage subsystem

Go to step 4.

You are using Out-of-Band management for ANY host attached to this storage subsystem

Before you insert a new controller canister into the storage subsystem, you must update the DHCP/BOOTP server for each Out-of-Band managed host so that it will associate the new controller's hardware Ethernet (MAC) address with the host name and IP address previously assigned to the removed controller.

To update the DHCP/BOOTP server, find the entry associated with the removed controller and replace its Ethernet (MAC) address with the new controller's Ethernet (MAC) address. The controller's Ethernet (MAC) address is located on an Ethernet ID label on the controller canister in the form xx.xx.xx.xx.xx.xx.

When you are finished, go to step 4.

From the Support tab, click the View Storage Subsystem Profile link, and then click the Controllers tab. Check the replacement part number of the remaining controller and ensure that the new controller has the same replacement part number.

If you do not have a controller with the appropriate replacement part number, contact your technical support representative.

Note: If the new controller canister does NOT contain a battery, insert the battery from the old controller canister into the new replacement controller canister. Consult your hardware documentation for details.

Make sure at least 1 minute has elapsed. Then, insert the new (compatible) controller canister firmly into place.

Place the new controller online.

a	From the Support tab, click the Manage Controllers link.
b	Click the Place Controller Online or Offline link.
c	Place the affected controller Online.

From the Support tab, click the View Storage Subsystem Profile link, and then click the Controllers tab.

Check the status of the controller. The controller should have an optimal status.

If you have logical drives mapped to hosts that have Automatic Logical Drive Transfer (ADT) disabled, it may be necessary to redistribute the logical drives to their preferred controller. Use the following steps to determine the ADT status of the hosts connected to your storage subsystem:

From the Support tab, click the View Storage Subsystem Profile link, and then click the Mappings tab.

Scroll to the NVSRAM Host Type Internal Definitions section.

If...

Then...

There are hosts mapped to logical drives on this storage subsystem that have an ADT status of disabled

There are hosts mapped to logical drives on this storage subsystem that are not running a host-based, multi-path failover driver

It may be necessary to redistribute the logical drives to their preferred controller. From the Support tab, click the Manage Controllers link, and then click the Redistribute Logical Drives link.

Note: If you have a mix of hosts with ADT enabled and ADT disabled, all logical drives will be immediately assigned back to their preferred path. However, until the host-based, multi-path failover driver detects the valid preferred path (may take several minutes), the logical drives mapped to the ADT-enabled hosts may get temporarily returned back to the non-preferred path.

Go to step 9.

All hosts mapped to logical drives on this storage subsystem have an ADT status of enabled

AND

All hosts mapped to logical drives on this storage subsystem are running a host-based, multi-path failover driver

No action is required.

If logical drives need to be redistributed to their preferred controller, the host-based, multi-path failover driver will automatically initiate the transfer.

Note that detection of a restored preferred path by the multi-path failover driver can take several minutes.

Go to step 9.

Click the Recheck button to rerun the Recovery Guru. The failure should no longer appear in the Summary area. If the failure appears again, contact your technical support representative.